The CA.Blocks.DataAccess has been published to NuGet. The first thing that you need to decide is which provider you want to use.

For SQL server https://www.nuget.org/packages/CA.Blocks.SQLServerDataAccess/

PM> Install-Package CA.Blocks.SQLServerDataAccess -Version x.x.x.

For SQL Microsoft.Data.Sqlite https://www.nuget.org/packages/CA.Blocks.SqliteDataAccess/

PM> Install-Package CA.Blocks.SqliteDataAccess -Version x.x.x

For SQL MySQL https://www.nuget.org/packages/CA.Blocks.MySQLDataAccess/

PM> Install-Package CA.Blocks.MySQLDataAccess -Version x.x.x

The second thing you need to do is set up a connection string see Connection String Examples

Then you will be ready to work with the DataAccess Class

Template example accessing SQL server

In this example, we going to use the data from the local SQL server selecting the data from the sysobjects table and executing the results into the .NET class calledExampleSysObjects below

    public class ExampleSysObjects
    {
        public int Id { get; set; }
        public string Name { get; set; }
        public string XType { get; set; }
        public DateTime CreateDate { get; set; }
    }

Template code using SQL server.

    public class YourDataAccessClass : SqlServerDataAccess
    {
        public YourDataAccessClass() : base( new SimpleConnectionStringDataAccessConfig("Server=(local);Database=tempdb;Integrated Security=SSPI;TrustServerCertificate=True"))
        {

        }

        public IList<ExampleSysObjects> ReadSysObjectsOfType(string xtype)
        {
            var cmd = CreateTextCommand("Select top 10 id as Id, name as Name, xtype as XType, crdate as CreateDate from sysobjects where xtype = @xtype").WithParameter(xtype.ToSqlParameter("@xtype"));
            return Execute(cmd).ToListOf<ExampleSysObjects>();
        }
    }

Notes:

1. The Class inherits from SqlServerDataAccess which is the SQL server provider.
2. The example above is using the provided SimpleConnectionStringDataAccessConfig, this is provided for quick prototyping, samples and testing code allowing connection to be specified in line with the code. It is recommended you use an external connection string when working on something that is to be published. see Connection String Examples
3. The ReadSysObjectsOfType method represents your DataAccess Method, the only input parameter exposed is xtype as a string, and the return type will be an IList of ExampleSysObjects
4. The CreateTextCommand will return an Interface to the SQL server implementation of the command
5. The SQL is constructed internally as parameterized query this is the developer's responsibility
6. The conversion of .NET string to SQL parameter is done using the WithParameter(type.ToSqlParameter("@xtype")); you can also use the connection object directly ie cmd.Parameters.Add(xtype.ToSqlParameter("@xtype"));
7. The ToSqlParameter is a convention used for taking a .NET type into a SQL server parameter. All .NET value types will have implementations of ToSqlParameter();
8. The cmd is then passed into the ExecuteToListOf method which returns the data as n IList of ExampleSysObjects. As we have 1-1 mapping the conversion is handled 100% by the Blocks.
9. The property names are case sensitive, so in this example, we have aliased the columns on the query side ie id as Id. This Id is the property name on the target object. You only have to do this if you using 100% automatic conversions

Consuming this class:

[Test]
public void ExecuteToListOfDev()
{
    var target = new YourDataAccessClass(); 
    var executeResult = target.ReadSysObjectsOfType("U"); 

    foreach (var o in executeResult)
    {
        TestContext.WriteLine($"{o.Id},{o.Name},{o.XType},{o.CreateDate}");
    }
}

Notes:

1. You construct the instance of the DataAccess YourDataAccessClass
2. You Call the method ReadSysObjectsOfType("U") The only methods you see are public ones from System.Object and the ReadSysObjectsOfType. This is by design the guts of the DataAccess class is protected by default. The Instance of the DataAccess can access the method, but the calling client only sees what is exposed. The calling code cannot call ExecuteToListOf

The dump result

-463397375,trace_xe_action_map,U ,30/04/2016 12:44:47 AM
-319884821,trace_xe_event_map,U ,30/04/2016 12:44:46 AM
117575457,spt_fallback_db,U ,8/04/2003 9:18:01 AM
133575514,spt_fallback_dev,U ,8/04/2003 9:18:02 AM
149575571,spt_fallback_usg,U ,8/04/2003 9:18:04 AM
1483152329,spt_monitor,U ,30/04/2016 12:46:37 AM
1787153412,MSreplication_options,U ,30/04/2016 12:47:59 AM